TPVM Complete Package Upgrade
You can perform a complete package
upgrade of TPVM.
You can upgrade a device‘s TPVM image when a TPVM is installed and running an XCO instance which is managing the
device. After the TPVM image update, an XCO instance gets reinstalled with the
same XCO version as before and rejoins with
the active XCO instance.
Note
- An upgrade from TPVM 4.5.x to TPVM 4.6.0 is a complete package upgrade.
- Change the TPVM password after you upgrade the SLX-OS version. This is due to
Ubuntu 20.04 LTS having a restriction with supporting certain special ASCII
characters. These special characters are required in storing TPVM password on
SLX-OS.
- TPVM Incremental upgrade is not supported.
For more information about commands and supported parameters, see
ExtremeCloud Orchestrator Command Reference,
3.6.0
Assumptions and Limitations
- XCO supports SLX-OS 20.3.2a and
later. The TPVM upgrade has SLX-OS dependencies for the new SLX commands:
tpvm
upgrade and tpvm revert. The
TPVM configurations has already been present in the SLX running-config.
- XCO does not support TPVM
upgrade on a single-node TPVM deployment.
- You can deploy a TPVM on multiple
high-availability (HA) nodes, but you can upgrade a TPVM only on the standby
TPVM node.
- TPVM upgrade is allowed only on
the XCO HA nodes that are managing
the devices and hosting the XCO HA instances.
- The XCO version is reinstalled and
remains the same after the TPVM upgrade. You must not perform an XCO version upgrade during a
TPVM upgrade. Ensure that you perform the XCO version upgrade before or after
the TPVM upgrade is completed on both the HA nodes.
- You can upgrade only one device‘s
TPVM at a time.
- User is required to change the TPVM password after upgrading to SLX-OS 20.5.1a.
This is due to Ubuntu 20.04 LTS having a restriction with supporting certain
special ASCII characters. These special characters are required in storing TPVM
password on SLX-OS.